chore(deps): update dependency pytest-cov to v7#594
chore(deps): update dependency pytest-cov to v7#594renovate[bot] wants to merge 1 commit intomainfrom
Conversation
|
Greptile SummaryAutomated dependency update bumping
Confidence Score: 1/5
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[pyproject.toml: pytest-cov==7.0.0] --> B{Python version?}
B -->|Python >= 3.9| C[pytest-cov 7.0.0 installs OK]
B -->|Python 3.8| D[Installation fails: requires >=3.9]
C --> E{uv.lock consistent?}
E -->|No: still pins 5.0.0| F[uv sync --locked fails or uses stale version]
E -->|Yes: regenerated| G[Tests run successfully]
D --> H[CI matrix includes 3.8 — build breaks]
Last reviewed commit: 53ad527 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| "pytest==8.3.4", | ||
| "pytest-asyncio==0.23.8", | ||
| "pytest-cov==5.0.0", | ||
| "pytest-cov==7.0.0", |
There was a problem hiding this comment.
Python 3.8 incompatibility with pytest-cov 7.x
pytest-cov==7.0.0 requires Python >=3.9 (dropped Python 3.8 support in v6.0.0). This project declares requires-python = ">=3.8" and the CI matrix tests against Python 3.8 (ci.yml line 20), so this upgrade will break Python 3.8 test environments.
Additionally, the uv.lock file was not regenerated — it still references pytest-cov==5.0.0, meaning uv sync --locked will fail or install the old version.
Options:
- If Python 3.8 support is still needed, pin to
pytest-cov==5.0.0(last version supporting 3.8). - If Python 3.8 can be dropped, update
requires-pythonand the CI matrix first, then upgrade pytest-cov and regenerate the lockfile.
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
1 participant
This PR contains the following updates:
==5.0.0→==7.0.0Release Notes
pytest-dev/pytest-cov (pytest-cov)
v7.0.0Compare Source
Dropped support for subprocesses measurement.
It was a feature added long time ago when coverage lacked a nice way to measure subprocesses created in tests.
It relied on a
.pthfile, there was no way to opt-out and it created bad interationswith
coverage's new patch system <https://coverage.readthedocs.io/en/latest/config.html#run-patch>_ addedin
7.10 <https://coverage.readthedocs.io/en/7.10.6/changes.html#version-7-10-0-2025-07-24>_.To migrate to this release you might need to enable the suprocess patch, example for
.coveragerc:.. code-block:: ini
[run]
patch = subprocess
This release also requires at least coverage 7.10.6.
Switched packaging to have metadata completely in
pyproject.tomland usehatchling <https://pypi.org/project/hatchling/>_ forbuilding.
Contributed by Ofek Lev in
#​551 <https://github.com/pytest-dev/pytest-cov/pull/551>_with some extras in
#​716 <https://github.com/pytest-dev/pytest-cov/pull/716>_.Removed some not really necessary testing deps like
six.v6.3.0Compare Source
Contributed by Marcos Boger in
#​712 <https://github.com/pytest-dev/pytest-cov/pull/712>_and
#​714 <https://github.com/pytest-dev/pytest-cov/pull/714>_.Anonymous contribution in
#​706 <https://github.com/pytest-dev/pytest-cov/pull/706>_.v6.2.1Compare Source
Added a version requirement for pytest's pluggy dependency (1.2.0, released 2023-06-21) that has the required new-style hookwrapper API.
Removed deprecated license classifier (packaging).
Disabled coverage warnings in two more situations where they have no value:
v6.2.0Compare Source
The plugin now adds 3 rules in the filter warnings configuration to prevent common coverage warnings being raised as obscure errors::
default:unclosed database in <sqlite3.Connection object at:ResourceWarning
once::PytestCovWarning
once::CoverageWarning
This fixes most of the bad interactions that are occurring on pytest 8.4 with
filterwarnings=error.The plugin will check if there already matching rules for the 3 categories
(
ResourceWarning,PytestCovWarning,CoverageWarning) and message (unclosed database in <sqlite3.Connection object at) before adding the filters.This means you can have this in your pytest configuration for complete oblivion (not recommended, if that is not clear)::
filterwarnings = [
"error",
"ignore:unclosed database in <sqlite3.Connection object at:ResourceWarning",
"ignore::PytestCovWarning",
"ignore::CoverageWarning",
]
v6.1.1Compare Source
--cov-contextand theno_covermarker are used together.v6.1.0Compare Source
Contributed by Tsvika Shapira in
#​678 <https://github.com/pytest-dev/pytest-cov/pull/678>_.#​675 <https://github.com/pytest-dev/pytest-cov/issues/675>_.--cov-precision.v6.0.0Compare Source
Now it will perform the check just like
coverage reportwould.--cov-precisioncli option that can override the value set in your coverage configuration.Configuration
📅 Schedule: Branch creation - "on the 15th day of the month before 12pm" in timezone UTC, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.